home *** CD-ROM | disk | FTP | other *** search
-
- The following has been changed with version 3.3.
-
- - Fixed the -registration and -debug options for the
- Shareware version. This was found during the beta
- testing of this version. The switches did not reliably
- function.
-
- - Registered users may now use -n instead of -nologo. The
- -n and -nologo are not recognized in the Shareware version.
-
- - Registered users may now use -r instead of the very long
- -registration switch. This brief switch is recognized only
- in the Registered version.
-
- - Removed the switch -m from the following programs:
-
- DISKTYPE.EXE
- RDI.EXE
- SDI.EXE
- WDI.EXE
-
- The time savings was no longer necessary. With no time
- savings, the contained code was unjustified. The time
- savings was closed upon through program code optimizations
- made in previous versions. The program CDI.EXE continues to
- allocate a large amount of memory; however, it is not
- believed that a user should encounter a situation where the
- transient part of the command interpreter will require a
- reload. Also, the program CDI.EXE probably will not work
- well under Microsoft Windows - any version. I doubt that it
- will ever be useful in this environment due to the amount of
- memory that it uses.
-
- - Added feature to the environment parameter SDIDEFAULT such
- that the user can place a colon and hyphen (:-) or colon and
- slash (:/) after the drive letter and then enter all desired
- default single letter parameters for the utilities. Where a
- parameter is not directly supported, the parameter will be
- ignored and no complaint will be displayed.
-
- Example:
- SET SDIDEFAULT=B:-itv
-
- This means to use drive B: unless A: is specified,
- continue on error, show progress in Track/Side format
- instead of percent complete, and verify writes to
- diskettes (WDI only).
-
- Redesignating the drive letter continues to be supported in
- the Shareware version; however, the new feature is only
- supported through registration.
-
- - Revised the registration authorization procedure such that
- all that is required for registration is a letter from the
- author providing information on how to use the program
- SWDIAUTH.EXE found with the Shareware version. Unless a
- very major change has been made to the package, registered
- users may obtain 'free' updates by downloading new versions
- and then running SWDIAUTH.EXE on the .exe files contained
- therein. A significant revision to the package may require
- new authorization information from the author at a nominal
- update price to be set at the time of the update.
-
- The following has been changed with version 3.2.
-
- - Modified the function which determines the diskette type
- such that the operation will stop if the user presses
- <ESC>. This was a very aggravating problem when either you
- forget to close the drive door, you forget to put a
- diskette into the drive or the diskette has never been
- formatted!
-
- The following has been changed with version 3.1.7.
-
- - I believe that the problem with the Intel 386DX-33
- motherboard has been fixed again. More crazy, undocumented
- behavior! I have made a preliminary contact with Intel to
- try to get them to look into fixing their BIOS
- incompatibilities.
-
- The following has been changed with version 3.1.6.
-
- - All command line arguments are now case independent.
-
- The following has been changed with version 3.1.5.
-
- - The command line arguments can be ganged together where
- sensible.
-
- - I have fixed the diskette I/O routines so that when <ESC>
- is pressed, it will stop more immediately. Previously, the
- program would finish the current track/head before checking
- for the <ESC> key.
-
- - I revised the diskette I/O routines and created a new
- problem with the Intel 386DX-33 motherboard. Getting tired
- of fighting the thing!
-
- The following items have been changed with version 3.1.4.
-
- - I have performed some code optimizations. The files
- should be slightly smaller and perhaps slightly faster.
-
- - I found an interesting bug with the -v parameter and with
- single disk drive comparing of diskettes:
-
- Consider the following code:
-
- for ( i = j = 0; i < 10; j = ( i++ ) )
- {
- /* whatever */
- }
-
- for ( i = j = 0; i < 10; j = ( ++i ) )
- {
- /* whatever */
- }
-
- When compiling with MSC 7.00A, the first loop initializes
- both i and j to 0. When the loop repeats, j is still 0 and
- i is 1!
-
- The second loop above will work?! Note that the elipses ()
- didn't force variable i to increment before assigning the
- result to j! I didn't use either case in this version,
- instead I simply incremented both i and j.
-
- for ( i = j = 0; i < 10; j++, i++ )
- {
- /* whatever */
- }
-
- The following items have been changed with version 3.1.3.
-
- - I have added a new option from the command line for all
- utilities that read from or write to diskettes -- -t. This
- option will allow the user to observe the progress in a way
- compatible to the MS-DOS format command prior to Version 4
- -- the progress will be displayed as Track XY Head Z.
-
- - I have added a new option from the command line for all
- utilities that read from or write to diskettes -- -m. See
- the next item for discussion.
-
- - I have changed the way in which these utilities allocate
- memory. Previously, these utilities would go out and
- allocate all memory not allocated including that occupied by
- the transient portion of the command interpreter. This
- automatic practice has now been discontinued. Instead, the
- utilities will allocate enough memory to hold both heads
- worth of information only. If the user desires to continue
- to allocate all available system memory, then he can specify
- a new switch -- -m to maximize the use of system memory.
- With this change, users can now run these utilities under
- Windows provided that the -m switch is not utilized.
-
- There are two items that have been changed with version 3.1.2.
- It is strongly recommended that the previous versions of these
- utilities be abandoned.
-
-
- - I have modified the function which determines the disktype
- such that it checks the first 40 tracks on a diskette. If
- any one returns successfully, then the diskette type will be
- returned.
-
- - I have permanently compressed all of the executable files
- with the Professional Version of PKLite Version 1.15. The
- logic for the program will check for this compression and if
- not present, they will not run.
-
-
- There is one item that has been changed with version 3.1.1.
-
-
- - I have modified the function which determines the disktype
- such that it checks the first 5 tracks on a diskette. If
- any one returns successfully, then the diskette type will be
- returned. Previously, the program expected both track 0 and
- the last track (either 39 or 79) to be good on at least one
- side. This has caused some problems in reading really flaky
- diskettes. I believe that this problem has been eliminated
- with this maintenance update.
-
-
- Several new features and repairs have been added to this SDI
- family of programs with version 3.1. The following outlines
- these issues:
-
-
- - The previous bug associated with a required reboot prior
- to using the format command has been fixed. This required
- making the function that read the diskette check the CMOS
- configuration information prior to trying to read the
- diskette. By performing this check first, the program no
- longer requests information for a diskette that the drive
- type does not support. Incidentally, this particular bug
- was observed only with the Intel 386DX-33 system. All other
- systems tested did not exhibit this particular problem.
- Maybe it's a bug with that particular BIOS....
-
- - The previous bug associated with writing to 1.44MB
- diskettes on an Intel 386DX-33 system has been eliminated.
- It seems that a BIOS call to write side 0 of a 1.44MB
- diskette would return without error that 36 sectors have
- been written even though it has only written the requested
- 18! The program allows for this particular return and
- accepts it as 'OK'. The BIOS on this machine does not
- return properly according to all BIOS reference documents
- that I have been able to look into. It is likely that this
- situation is a bug with the BIOS on this particular machine.
- If this does turn out to be a bug, the program will continue
- to work satisfactorily after the BIOS has been updated.
-
- - Two new programs have been added to the group:
- RDI.EXE -- Read Disk Information
- CDI.EXE -- Compare Disk Information
-
- - The default drive can be changed by configuring an
- environment variable (SDIDEFAULT).
-
- - Where appropriate MS-DOS style wildcards may be used to
- specify filenames.
-
- - SDI.EXE allows for multiple diskette saves.
-
- - WDI.EXE allows for multiple diskette writes.
-
- - Prompting for the diskette has been added to all programs.
- This can be overridden using a new skip prompt switch (-s).
-
- - DISKTYPE.EXE will now allow the user to test multiple
- diskettes on the specified drive without continuously
- running the program.
-
- - SDI.EXE has a new ignore error switch (-i) which allows
- the program to complete the diskette and show all bad areas
- found. If desired, this switch may be used with CDI.EXE.
- RDI.EXE automatically sets this switch when it is run.
-
- - WDI.EXE has a new verify switch (-v) which provides for
- reading the information written to the diskette and insuring
- that the information that was written is what the program
- has in memory that was supposed to be written.
-
- - All programs allow the user to press <ESC> to safely
- terminate the program. ^C will also terminate the program.
- Future versions will trap this variable and basically
- perform the <ESC> operation. At this time pressing ^C will
- abort the program without finishing writing the output to
- the disk file when running SDI.EXE.
-
- - Enhanced memory management has been employed to maximize
- the amount of memory available to the program as an
- intermediate buffer. This causes fewer periods of
- reading/writing to the hard disk drive. Because of the way
- in which these programs allocates memory, they should not be
- used with programs like Microsoft Windows. Use with these
- programs will cause a system wide failure! Also, you should
- not incorrectly configure the environment variable COMSPEC
- since these programs will kick the transient portion of
- COMMAND.COM out during their operation. MS-DOS
- automatically reloads the transient portion of COMMAND.COM
- after the program finishes running.
-
- - The operation for determining the diskette type has been
- rewritten and optimized. You should notice a much shorter
- delay prior to seeing the diskette type displayed on the
- screen.
-
- - Documentation has been written for the family of programs.
- Most users do prefer software that has some sort of
- documentation. Please forward any questions or comments so
- that these docs may be made as complete and correct as is
- possible!
-